Efficient instrumentation for code coverage testing
نویسندگان
چکیده
منابع مشابه
Code Coverage Analysis of Combinatorial Testing
Combinatorial t-way testing with small t is known as an e cient black-box testing technique to detect parameter interaction failures. So far, several empirical studies have reported the e↵ectiveness of t-way testing on fault detection abilities. However, few studies have investigated the e↵ectiveness of t-way testing on code coverage, which is one of the most important coverage criteria widely ...
متن کاملINSTRIM: Lightweight Instrumentation for Coverage-guided Fuzzing
Empowered by instrumentation, coverage-guided fuzzing monitors the program execution path taken by an input, and prioritizes inputs based on their contribution to code coverage. Although instrumenting every basic block ensures full visibility, it slows down the fuzzer and thus the speed of vulnerability discovery. This paper shows that thanks to common program structures (e.g., directed acyclic...
متن کاملEfficient mutation testing of multithreaded code
Mutation testing is a well-established method for measuring and improving the quality of test suites. A major cost of mutation testing is the time required to execute the test suite on all the mutants. This cost is even greater when the system under test is multithreaded: not only are test cases from the test suite executed on many mutants but also each test case is executed—or more precisely, ...
متن کاملAn Evaluation of Java Code Coverage Testing Tools
Code coverage metric is considered as the most important metric used in analysis of software projects for testing. Code coverage analysis also helps in the testing process by finding areas of a program not exercised by a set of test cases, creating additional test cases to increase coverage, and determine the quantitative measure of the code, which is an indirect measure of quality. There are a...
متن کاملEncoding Optimal Customized Coverage Instrumentation
Program coverage is an important software quality metric. Coverage is most commonly gathered in the testing lab during development. However, developers also sometimes use inexpensive forms of program coverage in production software. In the post-deployment scenario, users often place very strict requirements on tracing overheads and legal instrumentation strategies. This work deals specifically ...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: ACM SIGSOFT Software Engineering Notes
سال: 2002
ISSN: 0163-5948
DOI: 10.1145/566171.566186